Repository navigation
fix(agent): declare MiniMax native effort levels and no temperature for Pi and OpenCode - #298
Merged
Merged
Conversation
…or Pi and OpenCode
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
mmx agent setupnow declares the native MiniMax capabilities for Pi and OpenCode:MiniMax-M3.1-Flash: always thinks, effortlow/medium/high/xhigh/max(offandminimalmap to the lowest level instead of being sent; the API rejects disabled thinking),supportsTemperature: false.MiniMax-M3:supportsTemperature: false.temperature: falsefor both models.MiniMax-M3 and M3.1-Flash are open-weights models, so temperature is not a supported knob.
Tests:
bun test(614 pass),tsc --noEmit. Checked with Pi 1.3.0 against the CN API:output_config.effortis sent natively per level, no temperature, images work.Need help on this PR? Tag
@codesmith-botwith what you need.